Skip to content

Add suggested_experiment_status column to GeneratorRun#4886

Open
CristianLara wants to merge 1 commit intofacebook:mainfrom
CristianLara:export-D88091530
Open

Add suggested_experiment_status column to GeneratorRun#4886
CristianLara wants to merge 1 commit intofacebook:mainfrom
CristianLara:export-D88091530

Conversation

@CristianLara
Copy link
Contributor

Summary:

Summary

Add suggested_experiment_status column to GeneratorRun. Some benefits:

  1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
  2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing GS.gen() to return a tuple including the suggested_experiment_status but that over-complicated callsites.

AOSC DIFF

D92476170

Differential Revision: D88091530

@meta-cla meta-cla bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Feb 10, 2026
@meta-codesync
Copy link

meta-codesync bot commented Feb 10, 2026

@CristianLara has exported this pull request. If you are a Meta employee, you can view the originating Diff in D88091530.

@codecov-commenter
Copy link

codecov-commenter commented Feb 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.79%. Comparing base (5cf011e) to head (9873249).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4886   +/-   ##
=======================================
  Coverage   96.79%   96.79%           
=======================================
  Files         595      595           
  Lines       62841    62869   +28     
=======================================
+ Hits        60826    60854   +28     
  Misses       2015     2015           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 11, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 12, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 13, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 13, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 13, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 13, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
CristianLara added a commit to CristianLara/Ax that referenced this pull request Feb 13, 2026
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
Summary:

## Summary

Add `suggested_experiment_status` column to `GeneratorRun`. Some benefits:

1. We don't need to modify the GS.gen() or Orchestrator methods to pass along a suggested status via tuple, instead it's baked into the GeneratorRuns that are already being passed along
2. The suggested status are more clearly stored in the database for historical tracking

Prior to this approach I tried changing `GS.gen()` to return a tuple including the `suggested_experiment_status` but that over-complicated callsites.

## AOSC DIFF

D92476170

Reviewed By: lena-kashtelyan

Differential Revision: D88091530
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed Do not delete this pull request or issue due to inactivity. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants